-
Notifications
You must be signed in to change notification settings - Fork 0
docs: Add Promptless 1.0 launch blog post #176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
@Promptless actually i changed my mind, i don't want this in the Blog tab, i want it in the Docs tab, under Getting Started, between Welcome and Setup+Quickstart. also you should reference this in the right way (maybe a big card or something, figure out what works best) in the Welcome article |
for customer stories, vellum and the F500 ones are great, but in addition, let's include:
|
|
I've added new changes to address this PR comment in commit 6a54026 |
|
I've added new changes to address this PR comment in commit 77646e0 |
|
@Promptless here are a couple of images. you don't have to include all of them, but can you drop some of them into the right place?

|
|
I've added new changes to address this PR comment in commit 1728364 |
fern/docs/introducing-promptless.mdx
Outdated
| We launched Promptless 1.0 to solve a problem every team faces: keeping docs current is exhausting. Context gets lost in handoffs, updates lag behind releases, and support teams answer the same questions repeatedly because docs are always a step behind. | ||
|
|
||
| Promptless automatically drafts documentation updates based on your feature releases, support conversations, and internal discussions. It monitors your existing workflows and detects when documentation updates are needed—no prompt engineering required. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Promptless can you make this better? like you can say "We made Promptless to [xyz]" like you had.
"Promptless 1.0 represents a major leap forward in this [...]" describing both the improvements in suggestion quality and in the ways that promptless can improve docs in different ways.
doesn't have to be so brief.
| <img src="https://promptless-customer-doc-assets.s3.amazonaws.com/docs-images/org_2lvkgU9erOFxYhtEVVC0ymPrPdF/promptless-review-citations-1cc79d5c.png" alt="Promptless review interface showing documentation changes with inline citations linked to GitHub PRs" /> | ||
| </Frame> | ||
|
|
||
| ## How Teams Use Promptless |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Promptless this section needs an intro paragraph or something to summarize the different ways people use Promptless.
|
Promptless escalated the following message to you. If you respond, please remember to tag Promptless: I've addressed the content feedback:
Regarding the image transparency issue: The Frame component already has The Frame component can't add a background directly to the transparent parts of the images themselves. You'll need to recreate the images with a light grey background (or another solid color) baked into the image files to fix this issue. Let me know if you'd like me to help with anything else on this PR! |
|
@Promptless can you figure out how to make this page wider? |
|
Promptless escalated the following message to you. If you respond, please remember to tag Promptless: I've applied the content edits from your review:
Regarding making the page wider: Based on my research of the Fern documentation platform, there doesn't appear to be a frontmatter option or configuration setting to adjust individual page widths. Fern uses a consistent page width across all documentation pages. The main content area width is controlled at the theme/platform level rather than on a per-page basis. If you'd like a wider layout for this page specifically, you might need to:
Would you like me to investigate any specific aspect further, or is there a different approach you'd like to take? |
|
I've added new changes to address this PR comment in commit 9aae4f2 |
@Promptless can you take care of this |
|
I've added new changes to address this PR comment in commit fcf6b80 |
| We made Promptless to solve a problem every team faces: keeping documentation current is exhausting. Context gets lost in handoffs, updates lag behind releases, and support teams answer the same questions repeatedly because docs are always a step behind. | ||
|
|
||
| Promptless 1.0 represents a major leap forward in Promptless's abilities, dramatically improving suggestion quality and bringing in more capabilities to keep different types of content up to date. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Promptless here can you embed this video? https://www.youtube.com/watch?v=dvP8NAShrfQ
hopefully there's a native way to embed the video; otherwise lmk.











Creates a new blog post announcing Promptless 1.0 for a fresh audience (not just existing users). The post follows the successful themes from the YC launch post while highlighting the newer features built since then, including Voice Match, Promptless Capture, Screenshot Editor, Slack Listen, Citations, and Auto-Merge capabilities. The post emphasizes the core problem (keeping docs current is exhausting), how Promptless works, real customer proof points (Vellum, Clay, Fortune 500), and what's included in the 1.0 release.
Trigger Events
Open this suggestion in the Promptless dashboard
Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)